Skip to content

test(ci): exercise hosted gate outcomes - #10

Closed
qiyi71w wants to merge 4 commits into
plan/ci-responsibility-splitfrom
acceptance/ci-gates-454
Closed

test(ci): exercise hosted gate outcomes#10
qiyi71w wants to merge 4 commits into
plan/ci-responsibility-splitfrom
acceptance/ci-gates-454

Conversation

@qiyi71w

@qiyi71w qiyi71w commented Sep 11, 2026

Copy link
Copy Markdown
Owner

Temporary hosted acceptance for wimi321#454. Exercise failed, skipped, cancelled, and documentation-only CI scenarios against the candidate workflow. This PR will be closed without merging; production changes remain on plan/ci-responsibility-split.

Sourcery 总结

针对失败和跳过结果,测试托管 CI 门禁行为。

增强功能:

  • 测试托管 CI 对失败和跳过作业结果的处理。

CI:

  • 暂时将便携式脚本测试作业配置为失败,并禁用 Windows 脚本测试作业,以验证托管工作流。
Original summary in English

Sourcery 总结

针对失败、跳过、取消和仅文档变更场景,测试托管 CI 门禁结果。

增强:

  • 更新专门的验收指南,要求提供可复现的构建和运行时证据,以验证 Windows 桌面环境。

CI:

  • 通过禁用 Windows 脚本测试,测试托管 CI 门禁处理。

文档:

  • 将开发指南变更标记为仅文档变更,以便进行托管 CI 验收。
Original summary in English

Summary by Sourcery

Exercise hosted CI gate outcomes across failed, skipped, cancelled, and documentation-only scenarios.

Enhancements:

  • Update specialized acceptance guidance to require reproducible build and runtime evidence for Windows desktop validation.

CI:

  • Exercise hosted CI gate handling by disabling Windows script tests.

Documentation:

  • Mark the development guide change as documentation-only for hosted CI acceptance.

@sourcery-ai

sourcery-ai Bot commented Sep 11, 2026

Copy link
Copy Markdown
审查者指南(小型 PR 中折叠显示)

审查者指南

此临时的仅用于 CI 的 PR 修改了候选工作流,以测试托管环境中的失败和跳过作业结果:可移植脚本测试无条件失败,而 Windows 脚本测试被禁用;其中不包含任何生产实现变更。

托管 CI 门禁结果流程图

flowchart TD
    A[Hosted CI workflow] --> B[Portable script tests]
    A --> C[Windows script tests]
    B --> D[Failure: exit 1]
    C --> E[Skipped: if false]
    D --> F[Gate outcome exercised]
    E --> F
Loading

文件级变更

变更 详细信息 文件
强制可移植脚本测试作业产生失败结果,同时保留摘要构件上传。
  • 将可移植测试命令替换为无条件失败。
  • 通过现有的 always 条件确保失败时仍执行构件上传。
.github/workflows/ci.yml
禁用 Windows 脚本测试作业,以测试工作流跳过结果。
  • 添加作业级 false 条件,使该作业被跳过。
.github/workflows/ci.yml

提示和命令

与 Sourcery 交互

  • 触发新的审查: 在拉取请求中评论 @sourcery-ai review
  • 继续讨论: 直接回复 Sourcery 的审查评论。
  • 根据审查评论生成 GitHub issue: 回复审查评论,请 Sourcery 根据该评论创建 issue。你也可以在审查评论中回复 @sourcery-ai issue,以根据该评论创建 issue。
  • 生成拉取请求标题: 在拉取请求标题的任意位置写入 @sourcery-ai,即可随时生成标题。你也可以在拉取请求中评论 @sourcery-ai title,以随时生成或重新生成标题。
  • 生成拉取请求摘要: 在拉取请求正文中任意位置写入 @sourcery-ai summary,即可在指定位置随时生成 PR 摘要。你也可以在拉取请求中评论 @sourcery-ai summary,以随时生成或重新生成摘要。
  • 生成审查者指南: 在拉取请求中评论 @sourcery-ai guide,即可随时生成或重新生成审查者指南。
  • 解决所有 Sourcery 评论: 在拉取请求中评论 @sourcery-ai resolve,以解决所有 Sourcery 评论。如果你已经处理完所有评论并且不想再看到它们,这会很有用。
  • 关闭所有 Sourcery 审查: 在拉取请求中评论 @sourcery-ai dismiss,以关闭所有现有的 Sourcery 审查。如果你想从新的审查开始,这尤其有用——别忘了评论 @sourcery-ai review 来触发新的审查!

自定义使用体验

访问你的控制面板以:

  • 启用或禁用审查功能,例如 Sourcery 生成的拉取请求摘要、审查者指南等。
  • 更改审查语言。
  • 添加、删除或编辑自定义审查说明。
  • 调整其他审查设置。

获取帮助

Original review guide in English
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This temporary CI-only PR modifies the candidate workflow to exercise hosted failure and skipped job outcomes: the portable script tests fail unconditionally, while the Windows script tests are disabled; no production implementation changes are included.

Flow diagram for hosted CI gate outcomes

flowchart TD
    A[Hosted CI workflow] --> B[Portable script tests]
    A --> C[Windows script tests]
    B --> D[Failure: exit 1]
    C --> E[Skipped: if false]
    D --> F[Gate outcome exercised]
    E --> F
Loading

File-Level Changes

Change Details Files
Force the portable script-test job to produce a failed outcome while preserving summary artifact upload.
  • Replace the portable test command with an unconditional failure.
  • Keep artifact upload running on failure via the existing always condition.
.github/workflows/ci.yml
Disable the Windows script-test job to exercise a skipped workflow outcome.
  • Add a job-level false condition so the job is skipped.
.github/workflows/ci.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@qiyi71w qiyi71w closed this Sep 11, 2026
@qiyi71w
qiyi71w deleted the acceptance/ci-gates-454 branch September 11, 2026 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant